Comments
-
Issue solved! Just needed to add the current networks (LAN_SUBNET, LAN8_SUBNET) to the Users / Local Users & Groups / Local Users / VPN Access. We can now access each network.
-
Resolved. I was going in circles due to the need to "RESTART" the SonicWall after making certain changes. Access Rules and such were remaining and often I would lose Internet access. I reloaded the original configuration and started over from Step 1, after making some configuration changes, restarting the SonicWall at each…
-
Anyone available today? I think I have the final key, just need to know how to let the traffic pass/accept from the AUS_LAN_SUBNET (192.168.0.0/24) network through X5. So when I enable my NAT on the router, of course the IP address is changed to the same X5 subnet (192.168.100.0/30), traffic passes just fine. But when I…
-
Here is another trace, the SonicWall is dropping my ICMP and DNS packets at X5, which is all I am really sending at the moment:
-
I would think that the Interface Trust rule that automatically installed would work, But packets are not allow on X5 from 192.168.0.0/24
-
Update: I have set my router to routing only as below: LocalPCLAN = 192.168.0.5 Router = Eth1 (192.168.0.1) router gateway Router = Eth0 (192.168.100.1) router to firewall Firewall Port X5 = (192.168.100.2) firewall =================================================== The firewall is only allowing traffic from the…
-
The source IP is the SSLVPN Range. As the VPN is a virtual appliance from within the SonicWall, all SSLVPN users are assigned an address range of 192.168.0.221-192.168.0.240. This is how it is working now. I tried to use 10.10.10.0/24 as suggested, but external users could not access the local LAN. SSLVPN IP Pool is…
-
Ok, some more testing and now it looks like I have traffic forwarded, still not received. Here is my current config and results: Client Route - AUS_LAN_SUBNET (192.168.0.0/24) X5 Subnet (192.168.100.0/30) User VPN Access - AUS_LAN_SUBNET X5 Subnet Route - Source: SSLVPN Range Destination: AUS_LAN_SUBNET (192.168.0.0/24)…
-
Yes and X5 should be sending out the DNS or any traffic as my user has logged into the SSL VPN service, I should see something sent to the X5 egress port. I am thinking that I deselect the SSLVPN service (set to ANY) in my static route to allow ALL traffic....still testing.
-
Update:. When I set my Client Route and User/VPN Access both to "X5 Subnet", my packets get dropped by a policy, but I am not sure how to determine the policy in question:
-
Ok, testing now and the SonicWall is receiving my packets, my NetExtender is sending packets, but it appears the packets are not making it to the X5 Interface: no Egress Here is my current config: Access Object : Name: AUS_LAN_Subnet Zone Assignment: LAN Type: Network Network: 192.168.0.0 Netmask/Prefix length:…
-
Wonderful! I will try this along with the above implementation. I am guessing that when you introduce the Client Routes, that is the option that gives clients access to those exact resources.
-
Which is of an interesting topic. By the instructions of SonicWall SSLVPN setup, I must use an IP range directly related to my LAN to access my LAN resources at 192.168.0.0/24? Is this not the case? I would love to be able to assign a different IP address to the Client. As mentioned before, I inherited this and currently…
-
Thank for your suggestions, I will apply them here soon and let you know. The current setup allows Internet access and has been tested, it is ONLY the SSLVPN that is not seeing the local LAN. We are using 192.168.0.231 - ...0.240 as our upper IP range currently and have that blocked off by our DHCP server so there is no…